home *** CD-ROM | disk | FTP | other *** search
- Solution for maccrack's crackme written using VB6
- [http://www.mesa-sys.com/~eternal/crackmevb6.zip]
-
- Ok, well i needed a break from studying so i payed
- a visit the the famous crackme page and saw that
- finally someone did mine :-)
-
- Anyway i got this crackme cause lot of ppl still
- have problems with VB - and take it from me, VB is
- as easy as cracking other stuff
-
- The usual steps,
- 1) run crackme
- 2) get into reg box
- 3) fill, and let crackme check serial
-
- And we get a nice german nag telling us serial is
- wrong, anyway, the nag saves us all because since
- VB4-32 there's only one VB API call used for this
- purpose : rtcmsgbox
-
- Also the inputbox used in this crackme, and used
- alot in more general apps is created using a VB
- API function called : rtcinputbox - how nice, no?
-
- So,
- 1) bpx rtcmsgbox, works!
- 2) bpx rtcinputbox, works! xxxx:40208E
- enter fake serial : 123
-
- back in sice, check out eax :-), some code
- follows that moves our serial xxxx:4020AD
- and some code to free a bit of memory and
- then,
-
- :004020E9 mov dword ptr [ebp+FFFFFF50], 00401C50 (*)
- :004020F3 push ecx
- :004020F4 push edx
- :004020F5 mov dword ptr [ebp+FFFFFF48], 00008008
- :004020FF Call dword ptr [MSVBVM60.__vbaVarTstEq]
- :00402105 test ax, ax
- :00402108 je 004021B4
-
- once you get use to some VB code tracing
- you'll know enough after seeing this code
- check out 401C50, or ecx and edx
-
- remark, if u check out ecx/edx you'll see
- nothing at all - this is because VB uses
- some weird addressing mode, to fix this
- check memory ecx+8 and edx+8, there you'll
- find offset of your serial and the correct
- serial
-
- i found for ecx+8,
- 44 0F 51 .. .. ..
- and for edx+8,
- 50 1C 40 .. .. ..
-
- i hope the value in edx+8 rings a bell (*),
- if not go train your ASM knowledge a bit ;-)
-
- anyway, offset in ecx+8 is the one from our
- serial, edx+8 is the real serial : 3484
-
- Voila, solution this is my solution to this very
- easy crackme - all i can say is is that VB is
- not a problem, it all depends on the programmer
- if the protection is hard or easy, and this has
- nothing todo with the used programming language.
-
- Greetz to all my friends at mEXELiTE, cORE, REBELS, ...
- all regulars of #cracking, #cracking4newbies, ...
-
- and shoutout to MaCcrAck for this crackme.
-
- Vizion 08/1999.
-
- ps. - for all mistakes, typo's and other stuff
- contact my cat :-)
- - add the MSVBVM60.DLL to the export list
- before trying my solution